5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
- Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-8: Runtime Subroutine's and Predefined Processes

.UTIL ADD HOOK


This subroutine adds a record to the Hook file.

Usage:

Description:

This subroutine adds a record to the Hook file. All parameters are required, if any required parameters are missing, the subroutine will CANCEL.

<error_msg> will contain a detailed error message if the Hook record was not able to be added (Required). This must be PASSed Share "Y" to return the value.

--- HOOK RECORD is the record structure containing the Hook information (Required).

The fields are:

HOOK AP
HOOK VER
HOOK PROC TYPE
HOOK PROC NAM

The above fields identify the process to be hooked (Application, Version, Process Type, Process Name). This must be a valid process in the specified application/version.

HOOK OV DB: If you want the hook to switch the user to another database, enter that database here. Leave blank if you want the user to remain in their original database.

HOOK ACTIVE: Enter a Y to make this hook active the next time a user logs on. Blank or N means the hook is not active.

HOOK OV AP
HOOK OV VER
HOOK OV PROC TYPE
HOOK OV PROC NAM

The above fields identify the hook process (Application, Version, Process Type, Process Name). This must be a valid process in the specified application/version.

HOOK OV DB: If you want the hook to switch the user to another database, enter that database here. Leave blank if you want the user to remain in their original database.

HOOK ACTIVE: Enter a Y to make this hook active the next time a user logs on. Blank or N means the hook is not active.

This subroutine is different from .UTIL GET HOOK RECORDS / .UTIL PUT HOOK RECORDS in that the the changes are permanent, and they do not take effect immediately. If you want the changes to take effect immediately, use .UTIL GET HOOK RECORDS to get the current hook records from the engine, make the same changes as you did with this subroutine, then update the engine with .UTIL PUT HOOK RECORDS. Or you can do nothing, and the changes will take effect the next time users log on.

Also see .UTIL CHG HOOK and .UTIL DEL HOOK.

Note that although --- HOOK is an indexed file that can contain more than one record, only the current record buffer will be processed.

Application Design Manual                                         "Powered by Appx Software"

1168

©2006 By APPX Software, Inc. All Rights Reserved